What advice do you have for others considering Collibra Governance?

I would recommend Collibra Governance depending on the needs of the company. It's a very good tool but probably not suitable for all companies. I'd rate the solution nine out of ten.

I sometimes recommend Collibra Governance to our customers based on their requirements and environment. Most customers look forward to having a data lineage function, but I haven't seen any tool that satisfies the customer requirements, including Collibra Governance. The solution has primarily enabled some of the compliance reporting through data lineage reporting. When you have data cataloging with complete metadata enrichment and identification of PII and non-PII, it helps customers control and manage them properly. If a customer does not have the appetite to procure Collibra Governance because of the pricing models, we may recommend a different product with cheaper prices. Collibra is working on building a new product for AI governance. I want to see how Collibra's data governance and AI governance will relate to each other. Most of the customers we deal with are looking for a tool to resolve the data lineage challenge. However, none of the products in the market seem to be resolving the customers' data lineage issues. Vendors like Collibra, Alation, and Informatica could work on it and provide a more comprehensible solution to the customer. Overall, I rate the solution an eight out of ten.

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.

At our company, we have used the data catalog feature. Collibra Governance is the top data governance tool in the market. AI capabilities are already being introduced in Collibra Governance. The data lineage feature is also used in our company for data harvesting. Based on the business requirements, we customize the solution if needed. I would rate the solution an eight out of ten. I would recommend Collibra Governance to others.

Our current focus is more on the solution's stewardship, cataloging, and reference data features. The one feature of Collibra Governance we would like to explore is the automated tagging of PII data. We do deal with such kinds of data within our organization. It would be helpful if there were any videos available for us to go through because this is something that will help us in the near future. We are not extensively using the solution's data lineage functionality because we are simply building over it. The only challenge for us is from the connective side. We are not able to ingest all the data in Collibra, and that's why we cannot do element-to-element level data tracking. The major Broadlock would be the integration piece. If that is done, we'll be able to have all our data in the Collibra. The data lineage functionality is a really good feature, and we would really love to leverage it. The challenge is that the connectors are not available in the pipeline. Collibra Governance is deployed on the cloud in our organization. Overall, I rate the solution a seven out of ten.

Collibra Governance is deployed on the cloud in our organization. Overall, I rate Collibra Governance an eight out of ten.

I rate Collibra Governance an eight out of ten.

I recommend Collibra only when customers have a very sparse intake. Such as if they have primitive lineages and data sources that they cannot make obsolete or remove. Suppose they have varieties of intakes. In that case, I definitely would ask customers to go for Collibra. That's not because an intake can be integrated into Collibra. The profitability is that Collibra is integrated at the output end. The team is working on visualization. The service team is very preemptive and efficient. Collibra will give you a good scoop. If a company is vast enough and has various intakes, databases, and sources, Collibra is good for them. I rate Collibra a seven out of ten. Depending on the client, the rating may vary. If someone has told you that they have various sparse intakes and need to govern their data, Collibra will be a nine out of ten. But for a company with a limited intake, I would say that Collibra would be a load for them on the price side.

I recommend considering it, as it provides valuable features. It may be advisable to evaluate and assess the requirements and preferences of the client before making a final decision. I would rate the solution eight out of ten.

The maintenance is something that is carried out automatically by Collibra Governance. I rate the overall solution an eight out of ten.

I'm not sure which version of the solution we are on right now. We're on the cloud deployment, meaning we are likely using the latest iteration. I'd recommend the solution to others. It's a straightforward product. I would rate it nine out of ten overall.

We're just a customer. We fought pretty hard to have Collibra as opposed to Axon from Informatica. For us, getting Collibra was crucial, and we're really enjoying working with it. I'd advise people to start small and try to implement small pieces in a POC so you can gauge how it will work on a larger scale. It's important to really have a look at various use cases as well. You really want to work to sell it to the final users so that it will have a heavier adoption rate. I would rate the solution nine out of ten.

I would recommend this solution to others, and I would ask them to directly go for SaaS instead of going for on-prem because you get a lot more features. I believe the license is the same or similar, but I'm not really aware of the price points. The biggest lesson that I have learned from using Collibra is that being compliant is important, and we are helping our clients do that. You must have read about H&M and Citibank. They got charged a lot. I would rate Collibra Governance an eight out of ten. Because I'm not involved with SaaS, I am keeping two points away for that. After using SaaS for a year, I can say more, but for now, it is eight.

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 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.

In the company, there are more than three thousand users of Collibra Governance. My team has been using the solution daily, but I'm unsure of how frequently it's used by other teams. My rating for Collibra Governance is seven out of ten. My company is a customer of Collibra Governance.

I would rate Collibra Governance an eight out of ten.

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.

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.

I would rate this solution an eight out of ten.

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.

I'm only involved in the use of it. My advice would be to make sure that the content is of quality because it tends to mushroom into lots and lots of information that can easily get out of sync. It should only be entered into by an organization that has the discipline behind it to maintain the information at a high level of quality. Otherwise, you end up with a lot of information that seems useful, but in effect, it could be more harmful than it's worth if things get out of sync. It takes an organization to maintain this kind of solution. The content is dependent on the quality of the maintenance of the content. I see a small chunk of it, and I would rate it an eight out of ten.

I would rate this solution 8 out of 10. The entirety of Data Intelligence is good, but I can't talk about all the products inside. I can't give it a 10, at least for the pieces of Collibra that I know. There are many pieces of the platform, and I think everyone should at least test the Data Catalog and Data Privacy or deploy it and combine it. If we mix with other vendors that can deliver these things, it will be complex to get things done. It's very tight with the Data Catalog and Data Lineage. It's more than just an integration and an API for your services.

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.

While I do not have a sense of the version number, I would say that we are not on the latest version of the solution at this time. I would advise new users looking at getting it implemented to really use the out-of-box features before you overlay your specific strategy on it. Upfront investigations and creating a repeatable framework of how this will ultimately operate are important to the success of the solution. One of the crucial early factors is to get this as part of an operating fabric within your company. There's a lot of pre-work and pre-thought that needs to be in place in that sense. Having well-engaged business folks as part of it will help with the level of success as well. This is not necessarily a big bang type of development and release. It's very incremental. You've got to think backward as far as the user experience - of how things are going to be searched and located - and bring that back to your IT process. I'd rate the solution at a seven out of ten.

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.

If you know Collibra's history, the tool is fairly new to the market. It is maybe eight to 10 years old. Within the past three years, we've seen the Collibra platform, or the Collibra product, changing a lot and developing a lot. They've been incorporating a lot of user suggestions. I would say the DBA, the system we've learned, the product is still quite immature. However, it's developing. Earlier, they were using a few core APIs, which will now be deprecated in the newer version. Even though those are mapped to a newer functionality, it's an ever-changing thing. That does impact all your backend code and workflows. New users just need to be aware that it's still evolving. Collibra generally, is trying to incorporate as many new solutions into its product. That sometimes comes at the cost of an existing solution being removed due to coaligned abilities which you have already kind of implemented with the clients. It's kind of a reimplementation on the newer versions for a newer component. It's something to be aware of. From a client perspective, I rate it as a six out of ten. From a market perspective, I can rate it as a seven or eight. As much as I have heard that tool is comparatively unique and that lineage and the other capabilities like workflows that this brings to the table, compared to other products in the market, is kind of better. From a product perspective, I have to rate it as a six or a seven. And from a developer perspective, I'll rate it as a six. Overall, if I had to rate it on every aspect, I'd give it a seven out of ten.

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.

I work on governance modules. I'm not related to Collibra. I'm an external consultant and a governance consultant. We adopt any technology which is related to governance. We prepare ourselves and we'll learn it and we'll get hands-on experience so that we have a good understanding of it for our clients. My experience with Collibra has been amazing. I've been working on Collibra within a couple of fields and my journey through Collibra was very fabulous all the way across. I'm using the SaaS version of the solution. It ensures we're always up to date on the latest features, etc. I'd recommend the solution to others. I'd rate it at a seven out of ten. I'd rate it higher, however, the technical support is really quite bad.

We're just customers. We're end-users of the product. If a company wants to implement a solution more focused on the business aspects, this solution works well. However, if a company needs to, for example, have a solution that covers a 360 overview of a data governance implementation or a project where you have to collect business information, and also need to connect that business information to technical information, to create a data lineage and so on, there are other solutions that cover this part better. That said, Collibra is really user-friendly. It's really easy to use. For a non-technical business user, it's easy to access, to navigate information, and so on. Typically business users don't want to have an interface or don't want to use technical tools, so a company should be mindful of that. Overall, I would rate the solution at a seven out of ten.

Before you deploy or implement Collibra, just ensure that you have certain use cases that really qualify for leveraging Collibra. Assessment and evaluation are really important, first. Benefit analysis is the most important key. What are the transformational changes that Collibra is going to bring? If it's going to improve your ROI by deploying it, then migrate over to it; just don't do it because everyone else is doing it — that's not a good enough reason. There are certain tools out there that can analyze data and generate reports with a few simple clicks. Collibra doesn't work like that until you have the ground knowledge of the metamodel — how the backend works and how your assets should be categorized. You cannot expect to directly deploy Collibra. You need certain experts in that area who do extensive research and understand the backend of Collibra, only then can you proceed with it. Once you are pro with it, it becomes much easier, but initially, it does require some research and hard work. From what I have leveraged out of Collibra thus far, on a scale from one to ten, I would give it a rating of seven.

I would definitely recommend this solution, but I would say that before starting the implementation, just understand what the product is, what it can do, and what it cannot do. Don't focus too much on the technical aspects of the product. Data governance should be used from the business point of view. Data governance was a new concept for me. By using this product, I got to know a lot of different aspects of data governance, and how should you go about implementing it. One main lesson that I have learned from using this solution is that don't just focus on bringing the metadata from the whole system and dumping it into the tool. It will become unreadable for other users. You will end up with too much data that no one is using. It is better to start small. I would rate Collibra Governance an eight out of ten. There are two main bottlenecks for my use cases that can cause trouble for me. It needs better data lineage functionality for extracting the transformations. It also needs better integration. I would like to see more connectors and more flexibility in terms of integrating it with different systems.

Sometimes the technical support is messy but the system is great. It's a very good tool and I would suggest speaking directly with the technicians who develop the tool, rather than customer service. It's a great tool for a medium size company. if you're in a larger company, I would recommend implementing team by team. It's a tool that the end user needs to understand so if you implement it all at the one time, people will have difficulties and you won't have the support. I would rate this solution a seven out of 10.

Before using Collibra Governance for metadata development, you need a business analyst with extensive domain expertise. Collibra Governance is just a metadata creator. You need business knowledge to understand how you're going to create the metadata and how it will link with your business applications. Collibra Governance isn't the only part where you're going to develop everything. Collibra plays a major role, but you still have to add other components. For example, you need Java resources, Oracle and you need to integrate all this stuff into the Collibra before making the project list. It demands a high level of visibility. The technology component idea, database knowledge, and more should be made available to a select group of people. If that's not there and everyone is new, and you're using Collibra Governance for the first time, you're going to have many problems. The teams should have proper knowledge of background modeling, and they should have proper knowledge of the existing business. If they're creating a completely new team and the new team doesn't have any business knowledge, expect project failure. On a scale from one to ten, I would give Collibra Governance an eight.

Before purchasing a license or licenses for Collibra, you need to have a data strategy or data governance and a management strategy defined beforehand. You need to have at least some semblance of an idea of how you want the various spaces and communities in Collibra to be organized. Obviously, certain things will change as you get familiar with the tool, but you can't just wing it. You need to have a strategy that also takes into account other tools and other solutions that you want Collibra to be connected to because there could be an issue where maybe you have a data lineage tool that is getting upgraded in three months from now, and your current version of Collibra will be better suited to connect with that tool once it's been upgraded. You're never going to be able to know 100% beforehand when those types of events will happen, but you need to have some kind of strategy in mind. This is where you really need the investment in data governance and management before you define the tool that you're going to use. That has to come before any implementation of Collibra. It's a big tool, so it can potentially be difficult to implement if you don't have the right investment in place before deployment. It's also user-friendly with a lot of great out-of-the-box capabilities. There is some room for improvement in certain areas, but overall it's a good solution. I would rate this solution a seven out of 10.

We are Collibra Partners. We have a business relationship with the organization. If we have a Collibra expert on your team, it will be easy. Otherwise, new users should expect a bit of a learning curve. ANyone working closely with it should take some Collibra training alongside the product purchase. Professionals will help you and guide you in creating an organization level or department level unit with a glossary and everything. They can give you more insight. I'd also advise users to try to take the certification, which is free of cost in Collibra University, or try a partner training certification. Overall, I would rate the solution eight out of ten.

We are experts on implementing business-centric data governance programs, as that is the only model for success. As such, we are implementation partners with Collibra, and in fact are one of, if not the, longest-standing Collibra partners globally. The advice I'd give to other potential users would be the same I'd give to people implementing any sort of governance. I would first advise clients to have your data governance business cases ready in advance, or at least start by identifying potential business outcomes that can be delivered through clear and documented access to data. From there, they can target the relevant source systems needed to delivere on these business cases. From a technical perspective, there are different approaches to ingest structural metadata, i.e. tools and connectors that are available to assist with this. While Collibra is hands-down the best data governance collaboration platform, clients should review the different options to ingest metadata based on the targeted source systems. Of course, Collibra's catalog is the first option that should be considered, but available connectors need to be reviewed. Overall, on a scale from one to ten, I'd give it a nine. based on its excellence as a data governance business collaboration platform. From the perspective of metadata ingestion, I'd probably give it a seven - I like their current roadmap and designated approach, but connectors are a work in progress, as they are for everyone.